How to: interface with business logic using Web Services - soapUI
Introduction
All Exact Financials Enterprise business logic can be invoked as a Web Service. This document describes how to invoke the business logic Web Services using soapUI.
The following steps are involved:
- get entity definitions
- connect to login web service and get user object
- connect to entity web service and perform action
1. get entity definitions
The web services that have been deployed on the server can be viewed with the URL:
http://<server>:<port>/<wsa>/<wsa>/wsdl?
- server: the server on which the Apache Tomcat is running
- port: the port on which Apache Tomcat is listening (default: 8080)
- wsa: the name of the Progress OpenEdge web services adapter
This will list the web services that have been deployed:
Web Services Adapter Deployed Applications
| Name |
WSDL File |
Target URL |
| login |
login.wsdl |
urn:com.exact.efe:login |
| exceladdin |
exceladdin.wsdl |
urn:com.exact.efe.exceladdin |
| credit |
credit.wsdl |
urn:com.exact.efe:credit |
| mcomp |
mcomp.wsdl |
urn:com.exact.efe:mcomp |
Clicking on the WSDL file shows the WSDL. The URLs of the WSDLs can be added to your soapUI project which will then show the methods available:
The basic actions available for most entities are:
- assign
- create
- delete
- find
- search
- update
2. connect to login web service and get user object
The login web service (login.wsdl), when passed a valid user and password returns a user object.
If the user and password are correct and the user has 'login: web service' enabled in maintenance users then security data will be returned. The security data needs to be provided in business logic reqeuests.
3. connect to entity web service and perform action
In this example a search of all main classifications of company 621 are required. When calling search all records that match the search record are returned. It is important to make sure the values of fields that you do not want to use in your search are null. The easiest way to achieve this is to simply remove the elements / attributes from the SOAP message. Notice also the security data is filled with the value returned from the login web service:
A SOAP message is returned with all main classifications of company 621:
That's all.
Additional parameters
The input XML can contain an additional temp-table 'ttvariables'. This temp-table can contain the following fields:
- test_mode
- warnings_allowed
- field_list
- header_only
1. test mode
Can be used in create, update, delete and assign actions to check if the action will succeed. All checks are performed, the record is written to the database and if succesful the transaction is rolled back.
2. warnings allowed
Can be used in create, update, delete and assign actions to ignore functional warnings, for example when a cost center is filled but not used.
3. field list
Can be used in assign, find, update actions to only check or retrieve a limited set of fields. Note that the entity temp-tables also have a field_list field which will be used if the main field list is empty.
4. header_only
Can be used in find and update actions to indicate that any browse / line tables should be ignored. Note that this should only be used in combination with a field list of fields that do not depend on browse / line fields.
Start page Exact Financials Enterprise >
Connectivity > How to: interface with business logic using Web Services
| Main Category: |
Attachments & notes |
Document Type: |
Support - On-line help |
| Category: |
|
Security level: |
All - 0 |
| Sub category: |
|
Document ID: |
23.704.892 |
| Assortment: |
Exact Financials
|
Date: |
07-12-2020 |
| Release: |
7.03 |
Attachment: |
|
| Disclaimer |